-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ Add BusinessCore
source and Prefect tasks
#1051
Conversation
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
6616985 | Triggered | Generic Password | 883b504 | tests/integration/test_business_core.py | View secret |
6616985 | Triggered | Generic Password | 883b504 | tests/integration/test_business_core.py | View secret |
6616985 | Triggered | Generic Password | 1920067 | tests/integration/test_business_core.py | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
@judynah pls fix the linter errors before requesting review. You can ignore the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI not passing so not ready for review
BusinessCore
source and Prefect tasks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added my feedback
tests/integration/orchestration/prefect/flows/test_business_core_to_parquet.py
Outdated
Show resolved
Hide resolved
tests/integration/orchestration/prefect/tasks/test_business_core.py
Outdated
Show resolved
Hide resolved
src/viadot/orchestration/prefect/flows/business_core_to_parquet.py
Outdated
Show resolved
Hide resolved
src/viadot/orchestration/prefect/flows/business_core_to_parquet.py
Outdated
Show resolved
Hide resolved
46e0f6d
to
5475e76
Compare
Summary
Business Core connector migration from viadot 1 to viadot 2. Added
verify
parameter into utility functions.Importance
Required by the migration project.
Checklist
This PR:
CONTRIBUTING.md
CHANGELOG.md